Wearable device configuration using vehicle and cloud event data

ABSTRACT

A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on a user device that includes a processor and a memory, the memory storing instructions executable by the processor such that the device is programmed to: send a trigger configuration file to a vehicle computer in a vehicle; receive an indication of a trigger from the vehicle computer; receive an input from a wearable device; and execute a task, based on the input and the trigger. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a national stage of, and claims priority to, PatentCooperation Treaty Application No. PCT/US2015/058752, filed on Nov. 3,2015, which application is hereby incorporated herein by reference inits entirety.

BACKGROUND

A wearable device is a computer that is incorporated into items ofclothing and/or accessories, e.g., bracelets, pendants, etc., andtypically can comfortably be worn on the human body. Generally, wearabledevices have some form of communications capability, e.g., Bluetooth orthe like, and will allow the wearer access to local and global computersvia a wired or, usually, a wireless, network. Data-input capabilitiesare also a feature of such devices. Examples of wearable devices includewatches, glasses, contact lenses, e-textiles and smart fabrics,headbands, beanies and caps, jewelry such as rings, bracelets andhearing aid-like devices.

DRAWINGS

FIG. 1 is a block diagram of an exemplary event and reporting wearabledevice system.

FIG. 2 is a block diagram of an exemplary wearable device of the systemof FIG. 1.

FIG. 3 is a diagram of an exemplary process for initializing, monitoringvehicle events, and executing a task when a message is received from thewearable device.

FIG. 4 is a diagram of another exemplary process for monitoring vehiclesystems, a set of vehicle screens, and wearable actions.

DESCRIPTION Introduction

FIG. 1 is a block diagram of an exemplary event and reporting wearabledevice system 100. A vehicle 10 includes a computer 12 that communicatesthrough a user device 18 with a wearable device 20, which can be worn bythe vehicle 10 occupant, including the vehicle 10 operator. The wearabledevice 20 is typically a watch or a smartphone, but can also be a pairof glasses, a glove, a contact lens, a smart fabric, a headband, abeanie, a cap, a ring, a bracelet, an in-ear device, or the like, suchas is known for various applications, including acting as an externalhuman-machine interface (HMI) to the computer 12.

The computer 12 of a vehicle 10 reports a trigger, i.e., an indicationthat an event has been received in the vehicle 10 and/or at a vehiclecomponent of the vehicle 10, such as brakes, throttle, steering wheel,etc. to a user device 18 acting as an intermediary. The wearable device20 can then receive an input indication, such as an activation of aswitch on the wearable device 20, and send the user device 18 an inputindication signal. The user device 18, based upon a list of triggers anda list of input indication signals, can then send an appropriate messageto a human machine interface of the vehicle 10, a HMI of the user device18, a HMI of the wearable device 20 or even alert the occupant oranother by sending a text, an email to an email address, or the like.

Exemplary System Elements Vehicle

The vehicle 10 includes the vehicle computer 12 that includes aprocessor and a memory 14, the memory 14 including one or more forms ofcomputer-readable media. The memory 14 stores instructions executable bythe processor for performing various operations, including as disclosedherein. For example, the computer 12 generally includes instructionssuch that it is programmed to identify events and to provide a messageconcerning an event, e.g., to the user device 18. The computer 12 isfurther generally programmed to detect the presence(s) of the userdevice 18 and the wearable device 20. Accordingly, the computer 12 canprovide to or receive from the user device 18 and/or the wearable device20 files and messages that additionally are, or otherwise would be, sentto the human machine interface (HMI) 15. The user device 18, asexplained further below, in its role as an intermediary between thecomputer 12 and the wearable device 20, can receive data concerning oneor more triggers from the computer 12 and an input signal from thewearable device 20, and determine whether a message is to be provided tothe wearable device 20, the user device 18, the vehicle 10, or to anexternal network, and, if so, the form (e.g., haptic output, visualoutput instructions, text message, e-mail, etc.) of such a message aswell as its content (e.g., vibration indicating a danger situation, textdisplay indicating vehicle 10 speed, etc.)

The computer 12 is configured, i.e., includes programming and hardwaresuch as is known, for communicating with one or more servers 25 with adata store 30 via the vehicle 10 gateway 16. The gateway 16 can be atelematics unit or the like which accommodates sending and receivinginformation via an external network 28. The wearable device 20, the userdevice 18, and the vehicle 10 gateway 16 can communicate with eachother, as described below, and may include various wired and/or wirelessnetworking technologies, e.g., cellular, Wi-Fi, Bluetooth, Near FieldCommunication (NFC), wired and/or wireless packet networks, etc.Further, the computer 12 generally includes instructions for exchangingdata, e.g., from one or more wearable devices 20 and/or user devices 18and/or the HMI 15, which may be one or more of an interactive voiceresponse (IVR) system, a graphical user interface (GUI) including atouchscreen or the like, etc.

The vehicle 10 can have an additional electronic control units (ECUs) 13for monitoring and controlling various vehicle 10 electrical andelectromechanical systems. The ECUs can be incorporated into the vehicle10 and provide and request information to and from the occupant via theHMI 15, the wearable device 20, or the user device 18. For example, ECUs13 can represent a navigation ECU which provides a vehicle navigationsystem location. Other ECUs can include a safety ECU, a powertrain ECU,an entertainment ECU, just to name a few. The ECU 13 can contain aprocessor and a memory with instructions to be executed on the processorto perform each particular ECU's operation(s), as well as instructionson how to communicate with other ECUs and devices.

Wearable Device

The wearable device 20 is typically a device worn or carried by a userand may be any one of a variety of computing devices which includes aprocessor and a memory as well as having radio frequency and/or wiredcommunication capabilities. A concern of wearable device 20 is the sizeof the battery and how long the wearable will operate before needing abattery recharge or replacement. If the battery is large, the wearabledevice may be heavy, awkward to wear, or unsightly. To obtain areasonable operational time, while incorporating a less obtrusivebattery, the wearable device 20 will usually contain a low powerprocessor and a low power communications circuit. The low powercommunication circuit of the wearable device 20 may only be able tocommunicate with other devices within a very short range. For example,due to a very low radio frequency transmitter, the wearable device 20may only be capable of reliably communicating with the occupant's userdevice 18 when the wearable device 20 is within one meter of the userdevice 18. Therefore, the wearable device 20 could need to firstestablish a connection with the user device 18, and the user device 18may then handle the communications with the vehicle 10 computer 12. Inother words, a program executing on the user device 18 permits the userdevice 18 to act as an intermediary between the wearable device 20 andthe vehicle 10 computer 12.

In addition, the wearable device 20 may have a low power geolocationhardware and software circuitry to provide a wearable device location.For example, the wearable device 20 can report its locationindependently of the vehicle 10 navigation location or the user device18 location. The wearable device 20 location can then be used to verifythat the wearer of the wearable device 20 is within the vehicle 10 andhas not wandered away from the vehicle 10. In one example after awearable device 20 is not verified to be within, or within apredetermined distance of, a vehicle 10, a location alert message can besent to a concerned parent or child, e.g., to a user device 18.

Furthermore, the wearable device 20 can be used to supplement and/orreplace the HMI 15 of the vehicle 10. The wearable device 20 canexchange, i.e. send and/or receive messages with the user device 18 andthe user device 18 can exchange messages with the vehicle 10 computer12. For example, the computer 12 may generate an alert that is sent tothe user device 18. The user device 18 can determine whether to send amessage concerning the alert to the wearable device 20. Further, forexample, the user device 18 can include a query or a request in themessage sent to the wearable device 20 prompting for user input inresponse to the alert. The wearer of the wearable device 20 can thenpress a button or provide other input, which will then send a responseto the user device 18. In another example, the mere detection of thewearable device 20 within the vehicle 10 and proximate to the userdevice 18 can be considered as if a button was physically activated onthe wearable device 20 by a communications connection, e.g., theestablishment of a Bluetooth connection.

User Device

The user device 18 can be a smartphone, a tablet, or the like with atelecommunications connection to an external cellular network, as wellas local network capability. For example, the user device 18 can beconnected to a telephone network for voice communications as well ashaving a data connection to an external network, such as the Internet.The local network capability can be provided by WiFi, Bluetooth, NearField Communication, etc. The user device 18 can include geolocationhardware and software, which allows the device to obtain positionalinformation and provide a user device location.

The user device 18, typically a mobile device carried by a user, may beany one of a variety of computing devices with a processor and a memory,as well as a communication circuit. For example, the user device 18 maybe a portable computer, a tablet computer, a smart phone, etc., thatincludes capabilities for wireless communications using IEEE 802.11,Bluetooth, and/or cellular communications protocols. Further, the userdevice 18 may use such communication capabilities to communicate, e.g.,via a direct connection such a Bluetooth or the like and/or via thenetwork 28 with the vehicle computer 12 and the wearable device 20.Accordingly, the user device 18 may be used to carry out some of theoperations herein such as receiving environmental data from a server 25,making a determination to alert the driver of an impending storm andpossible flooded roadways, and providing and determining an alternativeroute for the vehicle 10. Further, the user device 18 could be used tosupplement and/or replace the HMI 15 of the vehicle 10.

FIG. 2 is a block diagram of an exemplary user device 18 intermediatingbetween the vehicle 10 and wearable device 20 with the capability toreceive external condition information and vehicle 10 status informationand send a wearable status message to the wearable device 20. Asdiscussed above, wearable devices can have limited computing andcommunications abilities. Therefore, software programs, such as asmartphone app or the like, permit the user device 18 to act as anintermediary between the vehicle 10 and the wearable device 20. Thevehicle 10 can send various driver activity signals, i.e., events asdescribed above, to the user device 18. For example, an accelerator(ACC) pedal position, a vehicle speed value, a steering wheel angle, avehicle health status, etc. may each generate an event, e.g., when avehicle speed exceeds a predetermined threshold, e.g., a certain valuein miles or kilometers per hour, a certain threshold over a speed limitdetermined by consulting a vehicle 10 navigation system, etc. The ACCpedal position is typically known as a “drive by wire” system and willdeliver information to the engine control ECU 13 about the acceleratorpedal position in addition to the information about the speed at whichthe driver is pushing on the gas pedal. In another example, the vehicle10 can send the vehicle health status to the user device 18 indicatingthe vehicle 10 is having issues with one or more systems. The userdevice 18 can then alert the operator of the wearable device 20 of thevehicle health status. The user device 18 can then query the operatorvia the wearable device 20 if the vehicle 10 health status should beuploaded to a vehicle service facility via the Internet. The operatorcan just acknowledge the upload by interacting with the HMI of thewearable device 20. Furthermore, the user device 18 can even negotiate aservice appointment with the vehicle service facility and send proposeddates and times to the wearable device 20 HMI, allowing the operator toselect a date and time that is acceptable. The user device 18 can thenconfirm the service appointment with the service facility.

The aforementioned driver activity signals permit the computer 12 and/oruser device 18 to determine a driver activity index, i.e., a valuerepresenting driver activity. Each of the activities can be quantifiedwith a number. For example, if the driver is pressing on the acceleratorto go faster, that action can be represented with a first factor driveractivity number, which can be relatively higher as compared to the nextdiscussed pedal positions. A midrange number would represent the driverholding a steady speed with the accelerator pedal. Likewise, if thedriver is not engaging the accelerator pedal, the driver activity numberfor the ACC driver activity would be lower. The vehicle speed can alsodetermine a second factor driver activity number, e.g., the faster thevehicle 10 is traveling, the higher the second factor driver activitynumber. An amount a steering wheel is turned is a third factor driveractivity number that may be considered in quantifying driver activity inthe driver activity index. The more the steering wheel is turned in oneexample, the higher the third factor driver activity number. The first,second, and third factor driver activity numbers are then aggregated,e.g., added or averaged, to determine an overall driver activity number.For example, the user device 18 ascertains that the ACC pedal positionindicates the driver is accelerating the vehicle through ACC pedalengagement, the vehicle 10 speed value is 55 miles per hour and thesteering wheel position is indicating a turn, the user device 18 candetermine that a driver is actively engaged in driving the vehicle andthe user device 18 can suppress notifications either the user device 18or the wearable device 20.

The computer 12 may provide one or more of a vehicle state data, whichcan contain a cluster screen state, a center stack screen state and aheads up display (HUD) state. The cluster screen state is a set ofinstrument data usually present on the dashboard of the vehicle 10, e.g.a speedometer and tachometer. The center stack screen state is a set ofvehicle control data usually present in the center stack of the vehicle10, e.g., radio, environmental, navigation, etc. The HUD state is a setof HUD data which may be projected upon the windshield in front of theoperator, e.g., a current speed limit, a vehicle speed of the vehicle10, etc.

In addition, the user device 18 and/or computer 12 can acquireenvironmental condition data as it relates to the vehicle 10 and itsjourney. For example, the user device 18 can request and obtain a set ofenvironmental conditions with regards to weather condition information,traffic condition information, and road condition information. Forexample, the set of environmental conditions can be requested by themobile device 18 from the server 25, which may be on the Internet. Theuser device 18 can then determine an event based on the environmentalconditions, e.g., because a predicted likelihood and/or intensity ofprecipitation is above a predetermined threshold, e.g., an 80% or higherlikelihood of rain; a prediction that an accumulation of precipitation,e.g., rain or snow within a predetermined time in a region of vehicle 10travel, will exceed a certain threshold; etc. Based on such event, theuser device 18 can be programmed to alert the driver of theenvironmental conditions either through the user device 18 and/or thewearable device 20. For example, an audio or visual message could bedisplayed on the user device 20 and the user could be prompted toprovide an input, e.g., pressing a soft or hard button, to acknowledgethe message.

The network 28 represents one or more mechanisms by which a vehicle 10computer 12 may communicate with a server 25 and/or a user device 18.Accordingly, the network 28 may be one or more of various wired orwireless communication mechanisms, including any desired combination ofwired (e.g., cable and fiber) and/or wireless (e.g., cellular, wireless,satellite, microwave, and radio frequency) communication mechanisms andany desired network topology (or topologies when multiple communicationmechanisms are utilized). Exemplary communication networks includewireless communication networks (e.g., using Bluetooth, IEEE 802.11,etc.), local area networks (LAN), and/or wide area networks (WAN),including the Internet, providing data communication services.

The server 25 may be one or more computer servers, each generallyincluding at least one processor and at least one memory, the memorystoring instructions executable by the processor, including instructionsfor carrying out various steps and processes described herein. Ingeneral, the server 25 may be used for a variety of purposes, e.g.,interacting with a vehicle 10 navigational system, providing data usedfor suggesting a vehicle 10 route and/or attributes thereof. The server25 may include or be communicatively coupled to a data store 30 forstoring data such as route information, potential waypoints, weather andtraffic information, etc. Thus, one possible operation of the server 25in the system 100 is to receive an indication from a vehicle 10 computer12 via the network 28 that a vehicle 10 occupant is in the vehicle 10,and that the vehicle 10 is on.

Exemplary Process Flows

FIG. 3 is a diagram of an exemplary process 100 for initializing andmonitoring one or more events and for obtaining input via a wearabledevice 20, whereupon a task may be executed, e.g., upon receipt of userinput to a wearable device 20, a simple message service (SMS) message orthe like may be sent to one or more recipients; e.g., based on a triggerfrom a vehicle 10 navigation system indicating that travel time isslower than usual, a SMS message may be sent to the wearable device 20wearer's spouse indicating the delay.

The process 100 begins in a block 105, in which the user device 18exchanges login credentials with the wearable device 20 and with thevehicle 10 computer 12. For example, a user who is wearing the wearabledevice 20 may be prompted to provide an input to the user device 18,e.g., via a smartphone app or the like, to initiate the exchange oflogin communications between the wearable device 20 and the user device18.

Next, in a block 110, the device 18 sends a trigger configuration fileto the vehicle 10 computer 12. The trigger configuration file containstriggers that the user device 18 wants the vehicle 10 to monitor andreport when the trigger occurs. For example, an ignition state, when thevehicle 10 is moving, an accelerator pedal position value, a vehiclehealth state, a steering wheel angle, etc., may be monitored andreported. Alternatively, the user device 18 can instruct the vehicle 10to download the trigger configuration file from the server 25 on thenetwork 28.

Additionally, the device 18 sends a wearable device configuration to thewearable device 20. The wearable device configuration can include a menuof tasks which are functions that the wearable device 20 can execute.For example, the wearable device 20 can be programmed with a “Help, I amlost” function or an “I am on my way” function. These functions can beprogrammed to a hard key, a soft key, a graphical user interface (GUI)interface, etc. For example, hard key and/or soft key programmingassociates a specific input on the wearable device 20, e.g., a soft keyand/or a hard key with a specific user response E.g., soft keyprogramming associated with a “travel time delayed” event could includeprogramming to send a message to a designated recipient upon selectionof the soft key, e.g., an SMS message informing a spouse of the delay. Ahard key is a dedicated hardware key, switch, slider, etc., on thewearable device 20. For example, an alert button on the wearable device20 that can send an emergency request to the user device 18, which inturn can call for emergency services or send a text requesting emergencyservices at a location of the vehicle 10, as provided by globalpositioning system (GPS) of the vehicle 10. A soft key is a buttonflexibly programmable to invoke any of a number of functions rather thanbeing associated with a single fixed function or a fixed set offunctions. The GUI of the wearable device 20 can be a LCD display, a LCDdisplay with a touch screen or merely a LED light which can flashdifferent patterns and colors to indicate various statuses of messagesto the user. For example, the LED can emit a green light when thevehicle 10 systems are operating normally and a red light when there isa problem with a system or subsystem.

Next, in a block 115, which can also execute after a block 120, thecomputer 12 monitors the vehicle 10 for an occurrence of one or moretriggers, e.g., as specified in the list of triggers. For example, theuser could have started the vehicle 10, in which case a change in theignition state would be reported to the user device 18.

Next, in the block 120, the computer 12 determines if the trigger didoccur. If a trigger occurred, next a block 125 is executed; otherwise,the block 115 is executed.

In the block 125, the computer 12 sends a message that the triggeroccurred to the user device 18. For example, a “vehicle is moving” eventmessage is sent once the vehicle 10 is in motion or a “vehicle is notmoving” when the vehicle 10 stops.

In a block 130, which can follow the block 125 but also can follow ablock 135, the user device 18 monitors the wearable device 20 for awearer device message which is generated when an input to the wearabledevice 20 occurs.

Next, in the block 135, a determination is made if the wearer devicemessage is received from the wearable device 20. For example, the usercould press and activate a soft key button to generate an “I am on myway” wearer device message. If the user device message is received, nexta block 140 is executed; otherwise, the system 100 executes in the block130.

In the block 140, a task is executed based upon the trigger and thewearer device message. For example, continuing with the example from theblocks 125 and 135, the task can be sending a message to a deviceoutside of the vehicle 10. In this example, the trigger indicates thatthe vehicle 10 is moving and the wearer device message is initiated bythe user input into the wearable device 20, whereupon the user device 18sends the “I am on my way” message to one or more designated recipients.Furthermore, the user device 18 can include a location message in thetext or email indicating that the user is in a vehicle and that thevehicle is moving.

The process 100 ends following the block 140.

FIG. 4 is a diagram of another exemplary process 200 for monitoringdriver activity and allowing appropriate communications of the wearabledevice 20.

The process 200 begins in a block 205, which is similar to the block105. Further, a block 210, following the block 205, is likewise similarto the block 110 described above.

Following the block 210, in a block 215, which can follow the blocks 210or 230, the vehicle 10 reports occurrences of events, if any, to thecomputer of the user device 18 from the list of triggers. For example,an ignition state, when the vehicle is moving, an accelerator pedalposition value, a vehicle health state, a steering wheel angle, etc.,may be monitored and reported.

Next in a block 220, the user device 18 receives an environmentalcondition report. For example, the report can include a weathercondition, a traffic condition, and a road condition related to thelocale the vehicle is located.

Next in a block 225, the user device 18 can send an alert message to thewearable device 20 based upon the list of triggers; the states of thecluster screen, center console, and the HUD; and the environmentalconditions. For example, the user device 18 receives information fromthe vehicle 10 that the vehicle 10 is traveling at a high rate of speed.The computer of the user device 18 also receives a weather conditionreport that a severe storm is in the path of travel of the vehicle 10.The computer of the user device 18 can send a message containing atravel report to the wearable device 20. The message can include analert which can be an audible alert, a haptic vibration, and/or anon-screen message on the wearable device 20 display.

Next, in a block 230 the computer of the user device 18 determineswhether the process 200 is complete. If so, the process 200 ends;otherwise, the process 200 returns to in the block 215.

CONCLUSION

As used herein, the adverb “substantially” means that a shape,structure, measurement, quantity, time, etc. may deviate from an exactdescribed geometry, distance, measurement, quantity, time, etc., becauseof imperfections in materials, machining, manufacturing, etc.

The term “exemplary” is used herein in the sense of signifying anexample, e.g., a reference to an “exemplary widget” should be read assimply referring to an example of a widget.

Computing devices such as those discussed herein generally each includeinstructions executable by one or more computing devices such as thoseidentified above, and for carrying out blocks or steps of processesdescribed above. For example, process blocks discussed above areembodied as computer-executable instructions.

Computer-executable instructions may be compiled or interpreted fromcomputer programs created using a variety of programming languagesand/or technologies, including, without limitation, and either alone orin combination, Java™, C, C++, C#, Visual Basic, Java Script, Python,Perl, HTML, etc. In general, a processor (e.g., a microprocessor)receives instructions, e.g., from a memory, a computer-readable medium,etc., and executes these instructions, thereby performing one or moreprocesses, including one or more of the processes described herein. Suchinstructions and other data may be stored and transmitted using avariety of computer-readable media. A file in a computing device isgenerally a collection of data stored on a computer readable medium,such as a storage medium, a random access memory, etc.

A computer-readable medium includes any medium that participates inproviding data (e.g., instructions), which may be read by a computer.Such a medium may take many forms, including, but not limited to,non-volatile media, volatile media, etc. Non-volatile media include, forexample, optical or magnetic disks and other persistent memory. Volatilemedia include dynamic random access memory (DRAM), which typicallyconstitutes a main memory. Common forms of computer-readable mediainclude, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, any other magnetic medium, a CD-ROM, DVD, any otheroptical medium, punch cards, paper tape, any other physical medium withpatterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any othermemory chip or cartridge, or any other medium from which a computer canread.

In the drawings, the same reference numbers indicate the same elements.Further, some or all of these elements could be changed. With regard tothe media, processes, systems, methods, etc. described herein, it shouldbe understood that, although the steps of such processes, etc. have beendescribed as occurring according to a certain ordered sequence, suchprocesses could be practiced with the described steps performed in anorder other than the order described herein. It further should beunderstood that certain steps could be performed simultaneously, thatother steps could be added, or that certain steps described herein couldbe omitted. In other words, the descriptions of processes herein areprovided for the purpose of illustrating certain embodiments, and shouldin no way be construed so as to limit the claimed invention.

Accordingly, it is to be understood that the above description isintended to be illustrative and not restrictive. Many embodiments andapplications other than the examples provided would be apparent to thoseof skill in the art upon reading the above description. The scope of theinvention should be determined, not with reference to the abovedescription, but should instead be determined with reference to theappended claims, along with the full scope of equivalents to which suchclaims are entitled. It is anticipated and intended that futuredevelopments will occur in the arts discussed herein, and that thedisclosed systems and methods will be incorporated into such futureembodiments. In sum, it should be understood that the invention iscapable of modification and variation and is limited only by thefollowing claims.

All terms used in the claims are intended to be given their broadestreasonable constructions and their ordinary meanings as understood bythose skilled in the art unless an explicit indication to the contraryin made herein. In particular, use of the singular articles such as “a,”“the,” “said,” etc. should be read to recite one or more of theindicated elements unless a claim recites an explicit limitation to thecontrary.

1.-20. (canceled)
 21. A user device that includes a processor and amemory, the memory storing instructions executable by the processor suchthat the device is programmed to: send a trigger configuration file to avehicle computer in a vehicle, the trigger configuration file containinga trigger for the vehicle computer to report occurrences of; receive anindication of the trigger from the vehicle computer; receive an inputfrom a wearable device; and execute a task, based on the input and thetrigger.
 22. The user device of claim 21, further programmed to instructthe vehicle computer to download the trigger configuration file from aserver on a network.
 23. The user device of claim 21, wherein thetrigger includes at least one of an accelerator pedal position value, anignition state, a vehicle speed, a vehicle health status and a steeringwheel angle.
 24. The user device of claim 21, further programmed to senda menu of tasks to the wearable device; and instruct the wearable deviceto display the menu of tasks on a human machine interface (HMI) of thewearable device.
 25. The user device of claim 21, wherein the wearabledevice is at least one of a watch, a smart phone, a pair of glasses, aglove, a contact lens, a smart fabric, a headband, a beanie, a cap, aring, a bracelet, and an in-ear device.
 26. The user device of claim 21,wherein the task sends a message to at least send a message to a HMI ofthe user device, a vehicle HMI, a HMI of the wearable device and aserver.
 27. The user device of claim 26, further programmed to determinea location of the vehicle using at least a user device location, avehicle navigation system location and a wearable device location; andexecute the task based in part the location of vehicle, the input fromthe wearable device and the trigger.
 28. The user device of claim 27,further programmed to: determine, using at least the user devicelocation, the vehicle navigation system location and the wearable devicelocation, that the wearable device location is not at the user devicelocation or the vehicle navigation system location; and execute the taskwith a location alert message indicating that the wearable devicelocation is not the user device location or the vehicle navigationsystem location.
 29. The user device of claim 26, further programmed to:receive environmental data that includes at least one of a weathercondition information, a traffic condition information and a roadcondition information; and execute the task with the message based inpart on the environmental data.
 30. The user device of claim 26, furtherprogrammed to: receive vehicle state data that includes at least one ofa cluster screen state, a center stack screen state, and a vehicle headsup display (HUD) state; and execute the task with the message based inpart on vehicle state data.
 31. A method comprising: sending a triggerconfiguration file to a vehicle computer in a vehicle, the triggerconfiguration file containing a trigger for the vehicle computer toreport occurrences of; receiving an indication of the trigger from thevehicle computer; receiving an input from a wearable device; andexecuting a task, based on the input and the trigger.
 32. The method ofclaim 31, further comprising instructing the vehicle computer todownload the trigger configuration file from a server on a network. 33.The method of claim 31, wherein the trigger includes at least one of anaccelerator pedal position value, an ignition state, a vehicle speed, avehicle health status and a steering wheel angle.
 34. The method ofclaim 31, further comprising sending a menu of tasks to the wearabledevice; and instruct the wearable device to display the menu of tasks ona human machine interface (HMI) of the wearable device.
 35. The methodof claim 31, wherein the wearable device is at least one of a watch, asmart phone, a pair of glasses, a glove, a contact lens, a smart fabric,a headband, a beanie, a cap, a ring, a bracelet, and an in-ear device.36. The method of claim 31, wherein the task sends a message to at leastsend a message to a HMI of a user device, a HMI of the vehicle, a HMI ofthe wearable device and a server.
 37. The method of claim 36, furthercomprising determining a location of the vehicle using at least a userdevice location, a vehicle navigation system location and a wearabledevice location; and execute the task based in part the location ofvehicle, the input from the wearable device and the trigger.
 38. Themethod of claim 37, further comprising: determining, using at least theuser device location, the vehicle navigation system location and thewearable device location, that the wearable device location is not atthe user device location or the vehicle navigation system location; andexecuting the task with a location alert message indicating that thewearable device location is not the user device location or the vehiclenavigation system location.
 39. The method of claim 36, furthercomprising: receiving environmental data that includes at least one of aweather condition information, a traffic condition information and aroad condition information; and executing the task with the messagebased in part on the environmental data.
 40. The method of claim 36,further comprising: receiving vehicle state data that includes at leastone of a cluster screen state, a center stack screen state, and avehicle heads up display (HUD) state; and executing the task with themessage based in part on the vehicle state data.